Provisioning of voice and other cs-domain services

ABSTRACT

Disclosed are devices and methods for provisioning of voice and other CS-domain services. A first server ( 22 ) comprises a call reception block ( 221 ) configured to receive an incoming voice call, from a first user equipment; a transmitting block ( 222 ) configured to send, in response to the reception of the incoming voice call, a paging request to a second server; a service request reception block ( 223 ) configured to receive, from the second server, an SGs service request message, and; a trigger block ( 224 ) configured to use the SGs service request message as a trigger to send an indication of user alerting to the first user equipment when the SGs service request message indicates that a second user equipment was in Connected mode.

CROSS-REFERENCE

The present application claims priority benefit to the followingapplications, which contents are all incorporated by reference herein:U.S. Provisional Application Nos. 61/253,078 filed on Oct. 20, 2009.

TECHNICAL FIELD

The present invention generally relates to devices and methods forprovisioning of voice and other CS-domain services.

BACKGROUND

As described in the specification 3GPP TS 23.272, the Circuit Switcheddomain Fallback feature (CSFB) in the Evolved Packet System (EPS) allowsfor provisioning of voice and other CS-domain services (e.g. SMS) byreuse of the CS infrastructure when the user equipment (UE) is served byEvolved UMTS Terrestrial Radio Access Network (E-UTRAN).

Specifically for the case of Mobile Terminated (MT) voice calls, theCSFB feature allows to page the mobile for CS domain MT calls while themobile camps in Idle mode on E-UTRAN cell or while the mobile isconnected to the EPC/E-UTRAN.

In both cases the mobile is eventually redirected to the legacyGERAN/UTRAN (GSM EDGE Radio Access Network/UMTS Terrestrial Radio AccessNetwork) access over which the CS domain call is eventually established.

In the pre-CS fallback terminating call establishment cases, the callmanagement signalling defined in the 3GPP 24.008 Technical Specificationtriggers state transitions in the network, as the call establishmentprogresses. In particular, once a proper radio channel has beenallocated to the called UE, the called UE may generate an ALERTINGmessage, which indicates the called user is being alerted, and triggersthe network to generate a ring-back tone towards the calling party.

However, in CS Fallback context, when the called user was in idle modeon the E-UTRAN side, if the network waits for the generation by thecalled UE of the ALERTING message (which can only be sent after the CSFallback procedure has taken place), the calling user will have to waitfor a very long time before being informed about the fact that thenetwork connected with the called user.

In CS Fallback context, when the called user was in connected mode onthe E-UTRAN side, the called user was already alerted of the MT call andrequested to accept/refuse the incoming call while it was still attachedto E-UTRAN.

If the called UE sent an ALERTING message to the network after gettingto UTRAN/GERAN, a ring-back tone would be generated towards the callingUE but that would mean the called user would need to accept the call asecond time or to wait for some additional time for the call to beestablished (if waiting for some time for the calling user to hear aringback tone before connecting the users). If the called UE sent a CALLCONFIRMED message directly followed by a CONNECT message withoutprevious ALERTING message, the calling user will not have heard aring-back tone before hearing the called user.

Overall this will result in poor user experience.

Embodiments of the present invention will improve the situation. Inparticular, embodiments of the invention aim at improving the userexperience of the calling party in the case of CS domain Fallback withmobile terminated calls.

SUMMARY

To address these needs, an aspect of the present invention relates to afirst server comprising:

a call reception block configured to receive an incoming voice call,from a first user equipment,

a transmitting block configured to send, in response to the reception ofthe incoming voice call, a paging request to a second server,

a service request reception block configured to receive, from the secondserver, an SGs service request message, and

a trigger block configured to use the SGs service request message as atrigger to send an indication of user alerting to the first userequipment when the SGs service request message indicates that a seconduser equipment was in Connected mode.

The server according to the invention thus aims at improving the userexperience of the calling party by allowing the calling party to knowthat the network is in the process of alerting the user on the calledparty side.

In some embodiments, the trigger block is further configured to, whenthe second user equipment was in Idle mode, use the SGs service requestmessage as a trigger to inform the calling party that the call isprogressing.

The server may further comprise a timer block configured to, when thesecond user equipment was in Connected mode, use the connected modeindication to start a Call Forwarding on No Reply timer.

Another aspect of the present invention relates to a method for mobileterminating call comprising the steps of:

receiving in a first server an incoming voice call, from a first userequipment, for a second user equipment,

transmitting from the first server, in response to the reception of theincoming voice call, a paging request to a second server,

receiving in the first server a SGs service request message from thesecond server, and

using in the first server the SGs service request message as a triggerto send an indication of user alerting to the first user equipment whenthe SGs service request message indicates that a second user equipmentwas in Connected mode.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings, in whichsame reference numerals refer to similar elements and in which:

FIG. 1 is a schematic block diagram of a Mobile Switching Centre server;

FIGS. 2 and 3 are schematic diagrams showing a network comprising theMobile Switching Centre server of FIG. 1 and steps of a method forestablishing a call between a first user equipment and a second userequipment of the network, according to a first embodiment of theinvention; and

FIGS. 4 and 5 are schematic diagrams showing a network comprising theMobile Switching Centre server of FIG. 1 and steps of a method forestablishing a call between a first user equipment and a second userequipment of the network, according to a second embodiment of theinvention.

DESCRIPTION OF PREFERRED EMBODIMENTS

Referring to FIG. 1 a Mobile Switching Centre (MSC) server 22 accordingto an embodiment of the invention comprises a call reception block 221configured to receive an incoming voice call, for example from a firstUser Equipment (UE) 1 (FIG. 2).

The MSC server 22 comprises a transmitting block 222 configured to send,in response to the reception of an incoming voice call, a Paging Requestto a Mobile Management Entity (MME) server 12 (FIG. 2).

The MSC server 22 comprises a service request reception block 223configured to receive, from the MME server 12, a SGs service requestmessage. The SGs service request message is described in specification3GPP TS 23.272. The SGs Service Request message contains an indicationthat a called UE was in Connected mode or in Idle mode.

The MSC server 22 further comprises a trigger block 224 configured touse the SGs service request message as a trigger to send an indicationof user alerting to the first UE 1 when the SGs service request messageindicates that a second User Equipment (UE) 2, which is the addressee ofthe call, was in Connected mode. In some embodiments of the invention,the trigger block 224 is further configured to use the SGs servicerequest message as a trigger to inform the calling party that the callis progressing when the second UE 2 was in Idle mode.

The MSC server 22 further comprises a timer block 225 configured to usethe connected mode indication of the SGs service request message tostart a Call Forwarding on No Reply timer when the second UE 2 was inConnected Mode.

FIG. 2 shows a telecommunication network comprising an E-UTRAN network10, a UTRAN/GERAN network 20, the first UE 1 and the second UE 2. TheE-UTRAN network 10 comprises an e-node B 11 and the MME server 12. TheUTRAN/GERAN network 20 comprises a RNC/BSC 21 and the MSC server 22.

Referring to FIGS. 2 and 3 we are describing a method for establishing acall according to an embodiment of the invention, in which the second UE2 is in Connected mode, or Active mode.

We consider that the user of the first UE 1 wants to call the user ofthe second UE 2.

The MSC 22 receives an incoming voice call from the first UE 1, assymbolized by arrow A1 in FIG. 2. The MSC 22 responds by sending aPaging Request to the MME 12, as symbolized by arrow A2.

The MME 12 receives the Paging Request from the MSC 22 and responds bysending a SGs Service Request message to the MSC 22, as symbolized byarrow A3. In this embodiment, as the second UE 2 is in Connected mode,the SGs Service Request message is sent right after the reception of thePaging Request and indicates to the MSC 22 that a signalling connectionexists for the second UE 2. In other words, the SGs Service Requestmessage contains an indication that the second UE 2 was in Connectedmode.

The effect of the SGs Service Request message is that the MSC 22considers the paging procedure as successful and stops a supervisiontimer for it.

Furthermore, upon reception of the SGs Service Request message, the MSC22 initiates the generation of ring-back tone towards the UE 1 of thecalling party, for example by sending an ISUP Address Complete Messagetowards a G-MSC. ISUP is part of the Signalling System which is used toset up telephone calls in Public Switched Telephone Networks. It isspecified by the ITU-T.

Thus, the MSC 22 is able to initiate the generation of ring-back tonewithout awaiting reception of a potential ALERTING message.

In the Connected mode, the MME 12 has an established connection with thee-node B 11 and reuses the existing connection to relay the PagingRequest to the second UE 2, as symbolized by arrow A4 a. The e-node B 11receives the Paging Request from the MME 12 and sends it to the secondUE 2, as symbolized by arrow A4 b. The Paging Request sent to the secondUE 2 contains a CN Domain indicator and a Caller Line Identification.

In response to the Paging Request, the second UE 2 needs to accept orreject the call. We consider here that the call is accepted. Then, thesecond UE 2 sends an Extended Service Request message to the MME 12, assymbolized by arrow A5 a. The node 11 receives the Extended ServiceRequest message from the second UE 2 and forwards it to the MME 12, assymbolized by arrow A5 b. The Extended Service Request message containsa CS Fallback Indicator indicating to the MME 12 to perform CS Fallback,as described in specification 3GPP TS 23.272.

In response to the reception of the Extended Service Request message,the MME 12 sends to the e-node B 11 an AP UE Context ModificationRequest message that includes a CS Fallback Indicator, as symbolized byarrow A6. This message indicates to the node 11 that the second UE 2 hasto be moved to UTRAN/GERAN network 20. The node 11 responds by sendingto the MME 12 a AP UE Context Modification Response message, assymbolized by arrow A7.

The second UE 2 is then moved to UTRAN/GERAN network 20, as symbolizedby arrow A_(UTRAN/GERAN), and a CS Call Establishment procedure isperformed, as symbolized by arrow A8 in FIG. 2. A CS call establishmentprocedure for MT calls is described in 3GPP TS 24.008 specification.

During this procedure, the MSC 22 sends a SETUP message to the second UE2, as symbolized by arrow A81 a in FIG. 1. The RNC/BSC 21 receives theSETUP message from the MSC 22 (embedded in a RANAP message) and forwardsit to the second UE 2, as symbolized by arrow A81 b.

The second UE 2 responds by sending to the MSC 22 a CALL CONFIRMEDmessage, as symbolized by arrow A82 a. This message is a confirmationthat the SETUP message was well received. The node 21 receives the CALLCONFIRMED message from the second UE 2 and forwards it to the MSC 22, assymbolized by arrow A82 b.

Immediately after the previous step, the second UE 2 sends a CONNECTmessage indicating that the communication can start.

FIG. 4 shows a telecommunication network similar to thetelecommunication network of FIG. 2. However, in the embodimentrepresented in FIGS. 4 and 5, we consider that the second UE 2 is inIdle mode.

The MSC 22 receives an incoming voice call from the first UE 1, assymbolized by arrow A101 in FIG. 4. The MSC 22 responds by sending aPaging Request to the MME 12, as symbolized by arrow A102.

The MME 12 receives the Paging Request from the MSC 22. Given that theUE 2 is in idle mode, the MME 12 needs to page the UE 2 in order tobring it to Connected mode.

Thus, the MME 12 responds to the Paging Request from the MSC 22 bysending a Paging Request intended to the second UE 2 and indicating thatthe page comes from the CS domain, as symbolized by arrow A103 a. Thee-node B 11 receives the Paging Request from the MME 12 and forwards itto the second UE 2, as symbolized by arrow A103 b.

The second UE 2 responds by sending to the MME 12 an Extended ServiceRequest message containing a CS Fallback Indicator, as symbolized byarrow A104 a. This message triggers the CS fallback procedure towardsthe legacy GERAN/UTRAN access. The node B 11 receives the ExtendedService Request message from the second UE 2 and forwards it to the MME12, as symbolized by arrow A104 b.

After the reception of the Extended Service Request message by the MME12, a SGs Service Request is sent from the MME 12 to the MSC 22, assymbolized by arrow A105, to indicate to the MSC 22 that a signallingconnection exists for this UE 2.

As previously described, this message causes the MSC 22 to stop asupervision timer for the paging procedure. Furthermore, upon receptionof the SGs Service Request message, the MSC 22 initiates the generationof ring-back tone towards the calling party, for example by sending anISUP Address Complete Message towards the G-MSC. Thus, the MSC 22 isable to initiate the generation of ring-back tone without awaitingreception of a potential ALERTING message.

Subsequently, the MME 12 sends to the e-node B 11 an 51-AP Initial UEContext setup message that includes a CS Fallback Indicator, assymbolized by arrow A106. This message indicates to the e-node B 11 thatthe second UE 2 has to be moved to UTRAN/GERAN network 20. The e-node B11 responds by sending to the MME 12 an S1-AP Initial UE Context SetupResponse message, as symbolized by arrow A107.

The second UE 2 is then steered to GERAN/UTRAN network, as symbolized byarrow A_(UTRAN/GERAN). Depending on the UE 2 capabilities and on thetarget access network capabilities, several options exist for the waythe second UE 2 is steered to UTRAN/GERAN. It can be done through a PShandover, through a network assisted cell change, or through an RRCconnection Release with redirection.

Then a CS Call Establishment procedure is performed, as symbolized byarrow A108. This procedure is similar to the procedure described inreference to FIGS. 2 and 3.

Thus, in both cases (Connected mode and Idle mode) the method accordingto the invention allows the calling party to know that the network is inthe process of alerting the user on the called party side.

Contrary to a ring-back tone used to inform a calling party that thephone of the called user is ringing, the present invention permits toinitiate the generation of ring-back tone towards the calling party assoon as the network gets in touch with the called mobile phone, i.e. assoon as the network gets a response from it, even if the called mobilephone is not necessarily ringing at this point.

It makes also use of the SGs signalling between the MME and the MSC totrigger state transition of the Connection Management state machine ofthe MSC, while before this invention, only Connection Managementmessages triggered such transitions.

While there has been illustrated and described what are presentlyconsidered to be preferred embodiments of the present invention, it willbe understood by those skilled in the art that various othermodifications may be made, and equivalents may be substituted, withoutdeparting from the true scope of the present invention. Additionally,many modifications may be made to adapt a particular situation to theteachings of the present invention without departing from the centralinventive concept described herein. Furthermore, an embodiment of thepresent invention may not include all of the features described above.Therefore, it is intended that the present invention not be limited tothe particular embodiments disclosed, but that the invention include allembodiments falling within the scope of the invention as broadly definedabove.

Expressions such as “comprise”, “include”, “incorporate”, “contain”,“is” and “have” are to be construed in a non-exclusive manner wheninterpreting the description and its associated claims, namely construedto allow for other items or components which are not explicitly definedalso to be present. Reference to the singular is also to be construed inbe a reference to the plural and vice versa.

A person skilled in the art will readily appreciate that variousparameters disclosed in the description may be modified and that variousembodiments disclosed may be combined without departing from the scopeof the invention.

1-3. (canceled)
 4. A server, comprising: a call reception blockconfigured to receive a signal for an incoming voice call; atransmitting block configured to send, in response to the reception ofthe incoming voice call, a paging request to a network entity; a servicerequest reception block configured to receive, from the network entity,a service request message including an indicator informing that a seconduser equipment (UE) was in an idle mode; and a trigger block configuredto use the service request message as a trigger to inform a first UEthat a call is progressing.
 5. The server of claim 4, wherein thenetwork entity is a Mobility Management Entity (MME).
 6. The server ofclaim 4, further comprising a timer block configured to, when the seconduser equipment was in Connected mode, use the connected mode indicationto start a Call Forwarding on No Reply timer.
 7. The server of claim 4,wherein the service request message allows the server to stopretransmitting the paging request message.
 8. The server of claim 4,wherein the paging request message and the service request message areexchanged via a SG interface between the server and the network entity.9. The server of claim 4, wherein if the server receives the servicerequest message, the server generates a ring-back tone without awaitinga reception of an ALERTING message.
 10. The server of claim 4, whereinthe server is a Mobile Switching Center.
 11. A method for receiving amobile terminating call, the method performed by a user equipment (UE)and comprising: receiving, by the UE in an idle mode and from an eNodeB,a paging message including a first indicator informing that a circuitswitching (CS) domain initiates the paging; performing, by the UE, aprocedure for establishing an RRC connection; and transmitting, from theUE and to a Mobile Management Entity (MME) via the eNodeB, a servicerequest message for falling back to a CS domain, such that the servicerequest message is used as a trigger to inform a calling party that acall is progressing.
 12. The method of claim 11, further comprisingperforming, by the UE, a handover procedure.
 13. The method of claim 11,wherein the service request message is encapsulated in at least one of aRRC message and an S1-AP message.